…n note + slot-semantics on MEMORY.md HTML comment (Amara round-10)

Three corrections from Amara round-10 review of PR #826
(now-merged fork-topology safety addendum):

1. Audit was missing rename/copy/type-change coverage. The
   slogan "same path is not same substrate" has an inverse:
   "different path can still be same substrate." Renames and
   copies need content comparison, not path equality.
   Replaced `--diff-filter=A` + `--diff-filter=M` with a
   single comprehensive `--diff-filter=ACMRT --find-renames`
   call + per-status interpretation guide.

2. Plumbing-vs-porcelain note added: human audit is fine with
   `git diff`; scripted tooling should prefer
   `git diff-tree -r --name-status --find-renames` (plumbing)
   for output stability + config-immunity, OR add
   `-c core.quotepath=false --no-ext-diff` to porcelain for
   predictability.

3. MEMORY.md HTML comment renamed `paired-edit:` →
   `latest-paired-edit:` per Amara: the comment is acting as
   a single-slot ledger that loses prior markers each time;
   making the slot semantics explicit prevents future
   confusion that only one paired edit exists. (The prior
   round-9 marker was overwritten without ledger preservation
   — a chronic drift class. Future enhancement: paired-edit
   log file if multi-slot history becomes necessary.)

Round-10 keepers preserved in audit prose:
  Added files are a clue.
  Modified shared files are the trap.
  Content equivalence is the gate.

The four meta-rules from the round-10 packet that are NOT
landing as new substrate (per B-0105 consolidation gate):
  - "Paired-edit failure must stop before commit" — process
    discipline; will absorb into existing paired-edit lint
    documentation when consolidation pass picks it up.
  - "Safety blockers should land as soon as green" —
    discipline-level rule; honored in this PR's intent.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…te pass + CI cost note (Amara round-11)

Three corrections to PR #827's fork-audit additions:

1. --diff-filter=ACMRT requires BOTH --find-renames AND
   --find-copies. Previous form had `C` in the filter but only
   enabled rename detection, so copied entries would never
   appear. Added --find-copies. Plumbing form likewise uses
   `-M -C`.

2. D=deleted moved to a SEPARATE pass. Not AceHack-content-
   loss in the AceHack→LFG hard-reset direction (LFG already
   lacks the file), but can be SEMANTIC REGRESSION if AceHack
   intentionally removed bad/stale/unsafe content. Review
   separately when the deleted path is workflow / security
   config / tooling / governance substrate.

3. Copy-detection cost note for CI tooling. -C has an O(n²)
   fallback comparing each added file to each deleted file.
   Added two-pass tooling pattern:
     fast pass — A/M/R/T with rename detection only
     slow pass — bounded -C (e.g. -l200) for suspicious clusters
   Human one-shot audit can stay unbounded.

Best round-11 keeper:
  Renames need -M.
  Copies need -C.
  Deletes need judgment.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>